Wireless link pairing authentication

ABSTRACT

Systems and methods include a medical device that matches an identifier received over its optical channel and associated with a control device within a line-of-sight of the medical device with an identifier received over its wireless channel and that automatically pairs with the control device associated with the matching identifier over its wireless channel, as well as, a control device that matches an identifier received over its optical channel and associated with a medical device within a line-of-sight of the control device with an identifier received over its wireless channel and that automatically pairs with the medical device associated with the matching identifier over its wireless channel, as well as, a first device and a second device that automatically pair over a wireless channel based on a location identifier received over an optical channel from a transmitter within a line-of-sight of the first device and the second device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application in a continuation of U.S. patent application Ser. No.16/889,259, filed Jun. 1, 2020, which claims priority to U.S.Provisional Patent Application Ser. No. 62/856,930, filed Jun. 4, 2019,entitled, “WIRELESS LINK PAIRING AUTHENTICATION,” the entirety of whichis incorporated by reference herein.

BACKGROUND Field

The present disclosure generally relates to systems and/or methods forpairing a medical device and a control device, and more specifically, tosystems and/or methods for pairing a medical device and a control deviceusing a line-of-sight optical link.

Technical Background

A medical facility may include a plurality of rooms where each room mayinclude a plurality of medical devices. Each medical device may bepermanently fixed within a room or movable between the plurality ofrooms. In addition, each medical device may be wirelessly controlled bya respective control device and the control device may be movablebetween the plurality of rooms. Accordingly, given the portable natureof medical devices and/or control devices, systems and/or methods aredesirable to ensure that a particular control device is in wirelesscommunication with a particular medical device. More specifically, ifwireless links are pairable, discoverable, and/or user-configurable,such systems and/or methods are desirable to ensure that a particularcontrolling device is paired to a particular medical device (e.g.,directly observable by a user) to prevent the unintended activationand/or control of a similar or identical medical device (e.g., locatedin an adjacent room) despite that similar or identical medical device'swireless link being accessible to the particular controlling device(e.g., through the room's wall).

Existing methods require some form of user intervention to either placepairable devices in a discoverable state and/or to manually select froma list of detected, pairable devices with which to pair. In suchaspects, placing a device in a discoverable state may be inconvenient tothe user and/or difficult for the user to remember or perform and manualselection of a device may result in the user selecting the wrong device.Ultimately, neither method is preferred since the user's focus is takenoff of a subject. Accordingly, systems and/or methods are desirable forefficiently, automatically, and correctly pairing a medical device and acontrol device.

SUMMARY

In one aspect, an automatically pairable medical device may include: afirst communication system configured to communicate via a firstcommunication channel, a second communication system configured tocommunicate via a second communication channel, a processor, and amemory storing program instructions, the program instructions, whenexecuted by the processor, causing the processor to: receive anidentifier associated with a control device within a line-of-sight ofthe medical device over the first communication channel, receive atleast one identifier associated with at least one control device overthe second communication channel, determine that the identifier receivedover the first communication channel matches an identifier of the atleast one identifier received over the second communication channel, andautomatically pair with the control device associated with the matchingidentifier over the second communication channel.

In such an aspect, according to some embodiments, the firstcommunication channel may be an optical communication channel and thesecond communication channel may be a wireless communication channel.Further in such embodiments, the optical communication channel may be aninfrared (IR) communication channel and the wireless communicationchannel may be a radio frequency (RF) communication channel. In otherembodiments, the program instructions may further cause the processorto: receive control inputs from the control device associated with thematching identifier, the control inputs for controlling a function ofthe medical device. In yet other embodiments, the program instructionsmay further cause the processor to: determine that at least one of thefirst communication channel or the second communication channel isassociated with a signal below a predetermined threshold strength, anddisassociate from the control device associated with the matchingidentifier. In further embodiments, the control device associated withthe matching identifier may be a first control device associated with afirst identifier, and the program instructions may further cause theprocessor to: receive a second identifier associated with a secondcontrol device within the line-of-sight of the medical device over thefirst communication channel, determine whether the first identifier isdetectable over the first communication channel, and remain paired withthe first control device if the first identifier is detected over thefirst communication channel, or automatically disassociate from thefirst control device if the first identifier is not detected over thefirst communication channel. Further in such embodiments, the programinstructions may further cause the processor to: determine that thesecond identifier received over the first communication channel matchesan identifier of the at least one identifier received over the secondcommunication channel, and automatically pair with the second controldevice associated with the matching second identifier over the secondcommunication channel.

In another aspect, an automatically pairable control device may include:a first communication system configured to communicate via a firstcommunication channel, a second communication system configured tocommunicate via a second communication channel, a processor, and amemory storing program instructions, the program instructions, whenexecuted by the processor, causing the processor to: receive anidentifier associated with a medical device within a line-of-sight ofthe control device over the first communication channel, receive atleast one identifier associated with at least one medical device overthe second communication channel, determine that the identifier receivedover the first communication channel matches an identifier of the atleast one identifier received over the second communication channel, andautomatically pair with the medical device associated with the matchingidentifier over the second communication channel.

In such another aspect, according to some embodiments, the firstcommunication channel may be an optical communication channel and thesecond communication channel may be a wireless communication channel.Further in such embodiments, the optical communication channel may be aninfrared (IR) communication channel and the wireless communicationchannel may be a radio frequency (RF) communication channel. In otherembodiments, the program instructions may further cause the processorto: transmit control inputs to the medical device associated with thematching identifier, the control inputs for controlling a function ofthe medical device. In yet other embodiments, the program instructionsmay further cause the processor to: determine that at least one of thefirst communication channel or the second communication channel isassociated with a signal below a predetermined threshold strength, anddisassociate from the medical device associated with the matchingidentifier. In further embodiments, the medical device associated withthe matching identifier may be a first medical device associated with afirst identifier, and the program instructions may further cause theprocessor to: receive a second identifier associated with a secondmedical device within the line-of-sight of the control device over thefirst communication channel, determine whether the first identifier isdetectable over the first communication channel, and remain paired withthe first medical device if the first identifier is detected over thefirst communication channel, or automatically disassociate from thefirst medical device if the first identifier is not detected over thefirst communication channel. Further in such embodiments, the programinstructions may further cause the processor to: determine that thesecond identifier received over the first communication channel matchesan identifier of the at least one identifier received over the secondcommunication channel, and automatically pair with the second medicaldevice associated with the matching second identifier over the secondcommunication channel. Yet further embodiments may include a userinterface system including at least one user interface control, and theprogram instructions may further cause the processor to: receive acontrol input via the at least one user interface control, send aninquiry token to the medical device associated with the matchingidentifier over the first communication channel, determine whether aresponse token has been received from the first medical deviceassociated with the matching identifier over the first communicationchannel, and transmit the control input to the medical device associatedwith the matching identifier if the response token has been receivedover the first communication channel, or abstain from transmitting thecontrol input to the medical device associated with the matchingidentifier if the response token has not been received over the firstcommunication channel. Yet another embodiment may include a visualindicator, and the program instructions may further cause the processorto: update the visual indicator to reflect that the medical device isnot within a line-of-sight of the control device.

In a further aspect, a system for automatically pairing devices mayinclude: a transmitter positioned within a location, the transmitterconfigured to transmit a location identifier over a first communicationchannel to devices with a line-of-sight of the transmitter, a firstdevice configured to: receive the location identifier over the firstcommunication channel, and transmit the location identifier and anidentifier associated with the first device over a second communicationchannel, a second device configured to: receive the location identifierover the first communication channel, and transmit the locationidentifier and an identifier associated with the second device over thesecond communication channel, where the first device is furtherconfigured to: scan the second communication channel for the locationidentifier received over the first communication channel, determine thatthe location identifier received over the first communication channelmatches a location identifier on the second communication channel,determine the second device identifier associated with the matchinglocation identifier, and automatically pair with the second deviceassociated with the second device identifier over the secondcommunication channel, and where the second device is further configuredto: scan the second communication channel for the location identifierreceived over the first communication channel, determine that thelocation identifier received over the first communication channelmatches a location identifier on the second communication channel,determine the first device identifier associated with the matchinglocation identifier, and automatically pair with the first deviceassociated with the first device identifier over the secondcommunication channel.

In such a further aspect, according to some embodiments, the firstcommunication channel may be an optical communication channel and thesecond communication channel may be a wireless communication channel.Further in such embodiments, the optical communication channel may be aninfrared (IR) communication channel and the wireless communicationchannel may be a radio frequency (RF) communication channel. In otherembodiments, the first communication channel may be an ultra-wide bandcommunication channel.

In yet another aspect, a method for automatically pairing a medicaldevice with a control device may include: receiving, via a firstcommunication channel, an identifier associated with a control devicewithin a line-of-sight of the medical device, receiving, via a secondcommunication channel different from the first communication channel, atleast one identifier associated with at least one control device,determining that the identifier received over the first communicationchannel matches an identifier of the at least one identifier receivedover the second communication channel, and automatically pairing withthe control device associated with the matching identifier over thesecond communication channel.

In such yet another aspect, according to some embodiments, the firstcommunication channel may be an optical communication channel and thesecond communication channel may be a wireless communication channel.Further in such embodiments, the optical communication channel may be aninfrared (IR) communication channel and the wireless communicationchannel may be a radio frequency (RF) communication channel. In otherembodiments, the method may further include: receiving control inputsfrom the control device associated with the matching identifier, thecontrol inputs for controlling a function of the medical device. In yetother embodiments, the method may further include: determining that atleast one of the first communication channel or the second communicationchannel is associated with a signal below a predetermined thresholdstrength, and disassociating from the control device associated with thematching identifier. In further embodiments, the control deviceassociated with the matching identifier may be a first control deviceassociated with a first identifier, and the method may further include:receiving, via the first communication channel, a second identifierassociated with a second control device within the line-of-sight of themedical device, determining whether the first identifier is detectableover the first communication channel, and remaining paired with thefirst control device if the first identifier is detected over the firstcommunication channel, or automatically disassociating from the firstcontrol device if the first identifier is not detected over the firstcommunication channel. Further in such embodiments, the method mayfurther include: determining that the second identifier received overthe first communication channel matches an identifier of the at leastone identifier received over the second communication channel, andautomatically pairing with the second control device associated with thematching second identifier over the second communication channel.

In yet a further aspect, a method for automatically pairing a controldevice with a medical device may include: receiving, via a firstcommunication channel, an identifier associated with a medical devicewithin a line-of-sight of the control device, receiving, via a secondcommunication channel different from the first communication channel, atleast one identifier associated with at least one medical device,determining that the identifier received over the first communicationchannel matches an identifier of the at least one identifier receivedover the second communication channel, and automatically pairing withthe medical device associated with the matching identifier over thesecond communication channel.

In such yet a further aspect, according to some embodiments, the firstcommunication channel may be an optical communication channel and thesecond communication channel may be a wireless communication channel.Further in such embodiments, the optical communication channel may be aninfrared (IR) communication channel and the wireless communicationchannel may be a radio frequency (RF) communication channel. In otherembodiments, the method may further include: transmitting control inputsto the medical device associated with the matching identifier, thecontrol inputs for controlling a function of the medical device. In yetother embodiments, the method may further include: determining that atleast one of the first communication channel or the second communicationchannel is associated with a signal below a predetermined thresholdstrength, and disassociating from the medical device associated with thematching identifier. In further embodiments, the medical deviceassociated with the matching identifier may be a first medical deviceassociated with a first identifier, and the method may further include:receiving, via the first communication channel, a second identifierassociated with a second medical device within the line-of-sight of thecontrol device, determining whether the first identifier is detectableover the first communication channel, and remaining paired with thefirst medical device if the first identifier is detected over the firstcommunication channel, or automatically disassociating from the firstmedical device if the first identifier is not detected over the firstcommunication channel. Further in such embodiments, the method mayfurther include: determining that the second identifier received overthe first communication channel matches an identifier of the at leastone identifier received over the second communication channel, andautomatically pairing with the second medical device associated with thematching second identifier over the second communication channel. In yetfurther embodiments, the method may further include: receiving, via atleast one user interface control, a control input, sending, via thefirst communication channel, an inquiry token to the medical deviceassociated with the matching identifier, determining, via the firstcommunication channel, whether a response token has been received fromthe first medical device associated with the matching identifier, andtransmitting the control input to the medical device associated with thematching identifier if the response token has been received over thefirst communication channel, or abstaining from transmitting the controlinput to the medical device associated with the matching identifier ifthe response token has not been received over the first communicationchannel. In yet another embodiment, the method may further include:updating a visual indicator to reflect that the medical device is notwithin a line-of-sight of the control device.

In still a further aspect, a method for automatically pairing devicesmay include: transmitting, via a transmitter positioned within alocation, a location identifier over a first communication channel todevices with a line-of-sight of the transmitter, receiving, by a firstdevice and a second device, the location identifier over the firstcommunication channel, transmitting, by the first device, the locationidentifier and an identifier associated with the first device over asecond communication channel, transmitting, by the second device, thelocation identifier and an identifier associated with the second deviceover the second communication channel, scanning, by the first device andthe second device, the second communication channel for the locationidentifier received over the first communication channel, determining,by the first device and the second device, that the location identifierreceived over the first communication channel matches a locationidentifier on the second communication channel, determining, by thefirst device, the second device identifier associated with the matchinglocation identifier and automatically pairing with the second deviceassociated with the second device identifier over the secondcommunication channel, and determining, by the second device, the firstdevice identifier associated with the matching location identifier, andautomatically pairing with the first device associated with the firstdevice identifier over the second communication channel.

In such still a further aspect, according to some embodiments, the firstcommunication channel may be an optical communication channel and thesecond communication channel may be a wireless communication channel.Further in such embodiments, the optical communication channel may be aninfrared (IR) communication channel and the wireless communicationchannel may be a radio frequency (RF) communication channel. In otherembodiments, the first communication channel is an ultra-wide bandcommunication channel.

Additional features and advantages of the embodiments described hereinwill be set forth in the detailed description which follows, and in partwill be readily apparent to those skilled in the art from thatdescription or recognized by practicing the embodiments describedherein, including the detailed description which follows, the claims, aswell as the appended drawings.

It is to be understood that both the foregoing general description andthe following detailed description describe various embodiments and areintended to provide an overview or framework for understanding thenature and character of the claimed subject matter. The accompanyingdrawings are included to provide a further understanding of the variousembodiments, and are incorporated into and constitute a part of thisspecification. The drawings illustrate the various embodiments describedherein, and together with the description serve to explain theprinciples and operations of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a block diagram illustrating a plurality of controldevices and a plurality of medical devices distributed amongst aplurality of rooms and a plurality of floors of a medical facility,according to one or more embodiments shown and described herein;

FIG. 2A depicts illustrative internal components of a control devicethat are communicatively coupled to one another to provide wireless linkpairing authentication with a medical device, according to one or moreembodiments shown and described herein;

FIG. 2B depicts illustrative internal components of a medical devicethat are communicatively coupled to one another to provide wireless linkpairing authentication with a control device, according to one or moreembodiments shown and described herein;

FIG. 3 depicts an illustrative wireless link pairing authenticationsystem including a rail-mounted lift as a medical device and a tetheredhand control unit, a wireless hand control unit, and/or a wall-mountedcontrol unit as control devices, according to one or more embodimentsshown and described herein;

FIG. 4A depicts an illustrative sling bar control unit as a controldevice, according to one or more embodiments shown and described herein;

FIG. 4B depicts an illustrative coupling control unit as a controldevice, according to one or more embodiments shown and described herein;

FIG. 5 depicts a flow diagram of an illustrative method for pairing amedical device and a control device using an optical communicationchannel, according to one or more embodiments shown and describedherein;

FIG. 6 depicts a flow diagram of another illustrative method for pairinga medical device and a control device using an optical communicationchannel, according to one or more embodiments shown and describedherein;

FIG. 7 depicts a flow diagram of an illustrative method for associatingand disassociating medical devices and control devices, according to oneor more embodiments shown and described herein; and

FIG. 8 depicts a flow diagram of an illustrative method for a controldevice to issue commands or control inputs to an authentically pairedmedical device, according to one or more embodiments shown and describedherein.

DETAILED DESCRIPTION

Reference will now be made in detail to embodiments to pair a medicaldevice and a control device using a line-of-sight optical link, examplesof which are illustrated in the accompanying drawings. Wheneverpossible, the same reference numerals will be used throughout thedrawings to refer to the same or like parts. Various embodiments of thepresent disclosure are depicted in FIG. 1. In general, a medicalfacility 100 may include a plurality of rooms and/or a plurality offloors (e.g., Rooms A and B on Floor 2 and Rooms C and D on Floor 1). Insuch aspects, a plurality of medical devices (e.g. MD_(A), MD_(B),MD_(C), and/or MD_(D)) and a plurality of control devices (e.g., CD_(A),CD_(B), CD_(C), and/or CD_(D)) may be distributed amongst the roomsand/or floors (see FIG. 1).

In one aspect, referring to FIG. 1, a control device (e.g., CD_(A)) anda medical device (e.g., MD_(A)) may be fixedly positioned within a room(e.g., Room A) and in line-of-sight of one another. Line-of-sight, forexample, may refer to an arrangement such that an optical system (e.g.,IR system) of a medical device and an optical system (e.g., IR system)of a control device have an unobstructed view of each other for emittedradiation (e.g., IR) to travel therebetween along a straight line orpath. According to such an aspect, the control device (e.g., CD_(A)) maywirelessly transmit (e.g., via a Bluetooth RF signal) its identifier(e.g., CD_(A) ID). Since a wireless signal may penetrate the wallsand/or floors of the medical facility 100, a number of medical devices(MD_(A), MD_(B), MD_(C), MD_(D), and/or the like) and/or a number ofcontrol devices (e.g., CD_(B), CD_(C), CD_(D), and/or the like) withinrange (e.g., up to 300 feet for Class 1 Bluetooth, up to 33 feet forClass 2 Bluetooth, and/or the like) may wirelessly receive theidentifier (e.g., CD_(A) ID). Further in such an aspect, the controldevice (e.g., CD_(A)) may optically transmit (e.g., via an IR opticalsignal) its identifier (e.g., CD_(A) ID) to medical devices (e.g.,MD_(A)) within its line-of-sight. Since an optical signal cannotpenetrate the walls and/or the floors of the medical facility 100, thecontrol device (e.g., CD_(A)) is only able to optically transmit itsidentifier (e.g., CD_(A) ID) to medical devices within its room (e.g.,MD_(A) in Room A). Yet further in such an aspect, each medical device(e.g., MD_(A)) optically receiving a control device identifier (e.g.,CD_(A) ID) via its optical communication channel (e.g., IR channel) maybe configured to scan its wireless communication channel (e.g., RFchannel) to determine whether the control device identifier (e.g.,CD_(A) ID) optically received via its optical communication channel(e.g., IR channel) matches a control device identifier wirelesslyreceived via its wireless communication channel (e.g., RF channel). If amatch exists, each medical device (e.g., MD_(A)) may be configured toautomatically authenticate the control device (e.g., CD_(A))corresponding to the matching identifier (e.g., CD_(A) ID) and to pairwith the authenticated control device (e.g., CD_(A)). After such anauthenticated pairing (e.g., one-way authentication), each medicaldevice (e.g., MD_(A)) may be configured to receive control signals fromthe authenticated control device (e.g., CD_(A)) over its wirelesscommunication channel (e.g., RF channel). In some aspects, after such anauthenticated pairing (e.g., one-way authentication), each medicaldevice (e.g., MD_(A)) may be configured to receive control signals fromthe authenticated control device (e.g., CD_(A)) over its opticalcommunication channel (e.g., IR channel). Still referring to FIG. 1,medical devices (e.g., MD_(B), MD_(C), MD_(D), and/or the like) that arenot within a line-of-sight of the control device (e.g., CD_(A)) will notoptically receive the optically transmitted identifier (e.g., CD_(A) ID)and thus will not be triggered to scan their respective wirelesscommunication channels for a matching control device identifier.

In another aspect, referring to FIG. 1, a medical device (e.g., MD_(A))and a control device (e.g., CD_(A)) may be fixedly positioned within aroom (e.g., Room A) and in line-of-sight of one another. According tosuch an aspect, the medical device (e.g., MD_(A)) may wirelesslytransmit (e.g., via a Bluetooth RF signal) its identifier (e.g., MD_(A)ID). Again, since a wireless signal may penetrate the walls and/orfloors of the medical facility 100, a number of medical devices and/or anumber of control devices (e.g., CD_(B), and/or the like) within rangemay wirelessly receive the identifier (e.g., MD_(A) ID). Further in suchan aspect, the medical device (e.g., MD_(A)) may optically transmit(e.g., via an IR optical signal) its identifier (e.g., MD_(A) ID) tocontrol devices (e.g., CD_(A)) within its line-of-sight. Again, since anoptical signal cannot penetrate the walls and/or the floors of themedical facility 100, the medical device (e.g., MD_(A)) is only able tooptically transmit its identifier (e.g., MD_(A) ID) to control deviceswithin its room (e.g., CD_(A) in Room A). Yet further in such an aspect,each control device (e.g., CD_(A)) optically receiving a medical deviceidentifier (e.g., MD_(A) ID) via its optical communication channel(e.g., IR channel) may be configured to scan its wireless communicationchannel (e.g., RF channel) to determine whether the medical deviceidentifier (e.g., MD_(A) ID) optically received via its opticalcommunication channel (e.g., IR channel) matches a medical deviceidentifier wirelessly received via its wireless communication channel(e.g., RF channel). If a match exists, each control device (e.g.,CD_(A)) may be configured to automatically authenticate the medicaldevice (e.g., MD_(A)) corresponding to the matching identifier (e.g.,MD_(A) ID) and to pair with the authenticated medical device (e.g.,MD_(A)). After such an authenticated pairing (e.g., one-wayauthentication), each control device (e.g., CD_(A)) may be configured totransmit control signals to the authenticated medical device (e.g.,MD_(A)) over its wireless communication channel (e.g., RF channel). Insome aspects, after such an authenticated pairing (e.g., one-wayauthentication), each control device (e.g., CD_(A)) may be configured totransmit control signals to the authenticated medical device (e.g.,MD_(A)) over its optical communication channel (e.g., IR channel).

In yet another aspect, referring to FIG. 1, the medical device (e.g.,MD_(A)) may authenticate the control device (e.g., CD_(A)) and thecontrol device (e.g., CD_(A)) may authenticate the medical device (e.g.,MD_(A)) as described above. In such an aspect (e.g., two-wayauthentication), only after the medical device (e.g., MD_(A)) pairs tothe authenticated control device (e.g., CD_(A)) and the control device(e.g., CD_(A)) pairs to the authenticated medical device (e.g., MD_(A)),may the control device (e.g., CD_(A)) transmit control signals to themedical device (e.g., MD_(A)) and the medical device (e.g., MD_(A))receive control signals from the control device (e.g., CD_(A)). Forpurposes of simplification, it should be appreciated that the variousembodiments described herein may employ either one-way authentication ortwo-way authentication without departing from the spirit and scope ofthe present disclosure.

In another aspect, referring to FIG. 1, a control device (e.g., CD_(C))and a medical device (e.g., MD_(C)) may not be fixedly positioned withina room (e.g., Room C) and may not be within line-of-sight of oneanother. According to such an aspect, the control device (e.g., CD_(C))may wirelessly transmit (e.g., via a Bluetooth RF signal) its identifier(e.g., CD_(C) ID) and a medical device (e.g., MD_(C)) positioned outsideof the room (e.g., Room C) and not within line-of-sight of any othercontrol device (e.g., CD_(A), CD_(B), CD_(D), and/or the like) maywirelessly receive the identifier (e.g., CD_(C) ID). Similar to above,the control device (e.g., CD_(C)) may optically transmit (e.g., via anIR optical signal) its identifier (e.g., CD_(C) ID). However, in view ofFIG. 1, since the medical device (e.g., MD_(C)) is not yet within aline-of-sight of the control device (e.g., CD_(C)) the medical device(e.g., MD_(C)) will not optically receive the control device identifier(e.g., CD_(C) ID) and will not be triggered to scan its wirelesscommunication channel for a matching control device identifier. However,after repositioning the medical device (e.g., MD_(C)) within the room(e.g., Room C) and within the line-of-sight of the control device (e.g.,CD_(C)), the medical device (e.g., MD_(C)) may optically receive thecontrol device identifier (e.g., CD_(C) ID) via its opticalcommunication channel and may be triggered to scan its wirelesscommunication channel for a matching control device identifier as wellas automatically authenticate and pair with the control device (e.g.,CD_(C)) associated with a matching control device identifier (e.g.,CD_(C) ID). The medical device (e.g., MD_(C)) may then be configured toreceive control inputs from the authenticated control device (e.g.CD_(C)) over its wireless communication channel. Yet further, in view ofFIG. 1, the medical device (e.g., MD_(C)), after being paired with anauthenticated control device (e.g., CD_(C)) may be repositioned withinanother room (e.g., Room D) without a line-of-sight of the controldevice (e.g., CD_(C)). According to various aspects of the presentdisclosure, after being paired with an authenticated control device(e.g., CD_(C)), a medical device (e.g., MD_(C)) may be furtherconfigured to monitor its optical communication channel for theauthenticated control device identifier (e.g., CD_(C) ID). In such anaspect, if the control device identifier (e.g., CD_(C) ID) is no longerbeing received over its optical communication channel, the medicaldevice (e.g., MD_(C)) may be configured to automatically disassociatefrom the control device (e.g., CD_(C)) over its wireless communicationchannel. However, after repositioning the medical device (e.g., MD_(C))within another room (e.g., Room D) and within the line-of-sight ofanother control device (e.g., CD_(D)), the medical device (e.g., MD_(C))may optically receive the control device identifier (e.g., CD_(D) ID)via its optical communication channel and may be triggered to scan itswireless communication channel for a matching control device identifieras well as automatically authenticate and pair with the control device(e.g., CD_(D)) associated with a matching control device identifier(e.g., CD_(D) ID). The medical device (e.g., MD_(C)) may then beconfigured to receive control inputs from the newly authenticatedcontrol device (e.g. CD_(D)) over its wireless communication channel. Insuch various aspects, although not specifically described, it should beappreciated that the control devices (e.g., CD_(C), CD_(D)) mayalternatively authenticate and pair with the medical device (e.g.,MD_(C)) via one-way authentication or the medical device (e.g., MD_(C))may authenticate and pair with the control devices (e.g., CD_(C),CD_(D)) and the control devices (e.g., CD_(C), CD_(D)) may authenticateand pair with the medical device (e.g., MD_(C)) via two-wayauthentication. Furthermore, similar to as described above, after beingpaired with an authenticated medical device (e.g., MD_(C)), the controldevices (e.g., CD_(C), CD_(D)) may be further configured to monitortheir respective optical communication channels for the authenticatedmedical device identifier (e.g., MD_(C) ID). In such an aspect, if themedical device identifier (e.g., MD_(C) ID) is no longer being receivedover their respective optical communication channels, the controldevices (e.g., CD_(C), CD_(D)) may be configured to automaticallydisassociate from the medical device (e.g., MD_(C)) over theirrespective wireless communication channels.

In a further aspect, a control device (e.g., CD_(D)) and a medicaldevice (e.g., MD_(D)) may not be fixedly positioned within a room (e.g.,Room D). For example, referring to FIG. 1, although the medical device(e.g., MD_(D)) may be repositioned, it may remain positioned within theline-of-sight of the control device (e.g., CD_(D)). Accordingly, thecontrol device (e.g., CD_(D)) and the (MD_(D)) may be authenticallypaired with one another as described herein (e.g., one-wayauthentication, two-way authentication). In this vein, as describedherein, another medical device (e.g., MD_(C)) may be positioned withinthe line-of-sight of the control device (e.g., CD_(D)) in the room(e.g., Room D). Accordingly, the control device (e.g., CD_(D)) mayoptically receive another medical device identifier (e.g., MD_(C) ID)via its optical communication channel (e.g., IR channel). In such anaspect, the control device (e.g., CD_(D)) may be configured to monitorits optical communication channel for the authenticated medical deviceidentifier (e.g., MD_(D) ID). In one example, if the authenticatedmedical device identifier (e.g., MD_(D) ID) is still being received overits optical communication channel, the control device (e.g., CD_(D)) maybe configured to remain authentically paired to the medical device(e.g., MD_(D)) and ignore the presence of the other medical device(e.g., MD_(C)). In an alternative example, if the authenticated medicaldevice identifier (e.g., MD_(D) ID) is still being received over itsoptical communication channel, the control device (e.g., CD_(D)) may beconfigured to further authenticate and pair with the other medicaldevice (e.g., MD_(C)).

In yet another aspect, referring to FIG. 1, a control device (e.g.,CD_(B)) and a medical device (e.g., MD_(B)) may or may not be fixedlypositioned within a room (e.g., Room B) in line-of-sight of one another.According to such an aspect, an IR transmitter (e.g., IRT_(B)) fixedwithin the room (e.g., Room B) may optically transmit a room identifier(e.g., RB ID) to control devices (e.g., CD_(B)) and medical devices(e.g., MD_(B)) within its line-of-sight. Again, since an optical signalcannot penetrate the walls and/or the floors of the medical facility100, the IR transmitter (e.g., IRT_(B)) is only able to opticallytransmit the room identifier (e.g., RB ID) to control devices andmedical devices within its room (e.g., Room B). In such an aspect, eachcontrol device (e.g., CD_(B)) that optically receives a room identifier(e.g., RB ID) via its optical communication channel (e.g., IR channel)may be configured to wirelessly transmit the received room identifier(e.g., RB ID) with its identifier (e.g., CD_(B) ID) over its wirelesscommunication channel (e.g., RF channel). Similarly, in such an aspect,each medical device (e.g., MD_(B)) that optically receives a roomidentifier (e.g., RB ID) via its optical communication channel (e.g., IRchannel) may be configured to wirelessly transmit the received roomidentifier (e.g., RB ID) with its identifier (e.g., MD_(B) ID) over itswireless communication channel (e.g., RF channel). In this vein, in oneexample, each control device (e.g., CD_(B)) that optically receives aroom identifier (e.g., RB ID) via its optical communication channel maybe further configured to scan its wireless communication channel todetermine whether the room identifier (e.g., RB ID) optically receivedvia its optical communication channel matches a room identifierwirelessly received via its wireless communication channel. If a matchexists, each control device (e.g., CD_(B)) may be configured toautomatically authenticate a medical device (e.g., MD_(B)) correspondingto the identifier (e.g., MD_(B) ID) wirelessly received with the roomidentifier (e.g., RB ID) over its wireless communication channel and topair with the authenticated medical device. After such an authenticatedpairing (e.g., one-way authentication), each control device (e.g.,CD_(B)) may be configured to transmit control signals to theauthenticated medical device (e.g., MD_(B)) over its wirelesscommunication channel. Similarly, in another example, each medicaldevice (e.g., MD_(B)) that optically receives a room identifier (e.g.,RB ID) via its optical communication channel may be further configuredto scan its wireless communication channel to determine whether the roomidentifier (e.g., RB ID) optically received via its opticalcommunication channel matches a room identifier wirelessly received viaits wireless communication channel. If a match exists, each medicaldevice (e.g., MD_(B)) may be configured to automatically authenticate acontrol device (e.g., CD_(B)) corresponding to the identifier (e.g.,CD_(B) ID) wirelessly received with the room identifier (e.g., RB ID)over its wireless communication channel and to pair with theauthenticated control device. After such an authenticated pairing (e.g.,one-way authentication), each medical device (e.g., MD_(B)) may beconfigured to receive control signals from the authenticated controldevice (e.g., CD_(B)) over its wireless communication channel. Yetfurther, in another example, the control device (e.g., CD_(B)) mayauthenticate the medical device (e.g., MD_(B)) and the medical device(e.g., MD_(B)) may authenticate the control device (e.g., CD_(B)) asdescribed. In such an aspect (e.g., two-way authentication), only afterthe control device (e.g., CD_(B)) pairs to the authenticated medicaldevice (e.g., MD_(B)) and the medical device (e.g., MD_(B)) pairs to theauthenticated control device (e.g., CD_(B)), may the control device(e.g., CD_(B)) transmit control signals to the medical device (e.g.,MD_(B)) and the medical device (e.g., MD_(B)) receive control signalsfrom the control device (e.g., CD_(B)). Still referring to FIG. 1,medical devices (e.g., MD_(A), MD_(C), MD_(D), and/or the like) andcontrol devices (e.g., CD_(A), CD_(C), CD_(D), and/or the like) that arenot within a line-of-sight of the IR transmitter (e.g., IRT_(B)) willnot optically receive the optically transmitted room identifier (e.g.,RB ID) and thus will not be triggered to scan their respective wirelesscommunication channels for a matching room identifier.

According to alternative aspects of the present disclosure, the opticalcommunication channel as described herein may be supplanted by or usedin combination with another communication channel (e.g., a differentnon-RF communication channel, a non-audible (e.g., ultrasonic)communication channel, and/or the like) without departing from thespirit and scope of the present disclosure.

FIG. 2A depicts illustrative internal components of a control device 200that are communicatively coupled to one another to provide wireless linkpairing authentication with a medical device, according to one or moreembodiments of the present disclosure. As shown in FIG. 2A, the controldevice 200 may include a local interface 202 (e.g., a bus) thatcommunicatively interconnects the various components, including, but notlimited to, a processing device 204, memory 206, input/output hardware208, network interface hardware 210, and/or a data storage device 212.

The processing device 204, such as a computer processing unit (CPU), maybe the central processing unit of the control device 200, performingcalculations and logic operations required to execute a program. Theprocessing device 204, alone or in conjunction with one or more of theother elements disclosed in FIG. 2A, is an illustrative processingdevice, computing device, processor, or combination thereof, as suchterms are used in this disclosure.

The memory 206, such as read only memory (ROM) and random access memory(RAM), may constitute illustrative memory devices (i.e., non-transitory,processor-readable storage media). Such memory 206 may include one ormore programming instructions thereon that, when executed by theprocessing device 204, cause the processing device 204 to completevarious processes, such as the processes described herein. Optionally,the program instructions may be stored on a tangible computer-readablemedium such as a digital disk, flash memory, a memory card, a USB drive,an optical disc storage medium (e.g., Blu-ray™, CD, DVD), and/or othernon-transitory processor-readable storage media.

In some embodiments, the program instructions contained on the memory206 may be embodied as a plurality of software modules, where eachmodule provides programming instructions for completing one or moretasks. For example, as shown in FIG. 2A, the memory 206 may contain oneor more of operating logic 214, communications logic 216, and UI logic218. It should be understood that the various logic modules describedherein with respect to FIG. 2A are merely illustrative, and that otherlogic modules, including logic modules that combine the functionality oftwo or more of the modules described hereinabove, may be used withoutdeparting from the scope of the present disclosure.

Still referring to FIG. 2A, the data storage device 212, which maygenerally be a storage medium that is separate from the memory 206, maycontain a data repository for storing electronic data and/or the likerelating to the location of the control device 200, an identification ofthe control device 200, configuration settings, UI data, and/or thelike. The data storage device 212 may be any physical storage medium,including, but not limited to, a hard disk drive (HDD), memory,removable storage, and/or the like. While the data storage device 212 isdepicted as a local device, it should be understood that the datastorage device 212 may be a remote storage device that is remotelylocated from the control device 200, such as, for example, a servercomputing device or the like.

Illustrative data that may be contained within the data storage device212 may include, for example, location data 220, configuration data 222,UI data 224, pairing data 226, and/or the like. Pairing data 226 mayinclude one or more medical device identifiers to which the controldevice 200 is or has been authentically paired via the methods asdescribed herein.

The input/output hardware 208 may generally include an IR system 228, awireless system 230, an indicator 232, a location system 234, and a userinterface system 236. The IR system 228 may include an IR diode 238(e.g., infrared LED) configured to emit/transmit infrared light and aphoto transistor 240 configured to receive infrared light and to convertthe infrared light into an electric current (e.g., according to IRprotocols). The IR system 228 may be unidirectional (e.g., phototransistor 240 shown in phantom as optional) or bidirectional (e.g.,including the photo transistor 240). Furthermore, the photo transistor240 may be omni-directional to receive misaligned (e.g., within adefined tolerance) and/or reflected (e.g., off a wall, an object withinthe room, and/or the like) optical signals. According to various aspectsthe IR system 278 may include a transceiver module. The wireless system230 may include a transceiver 242 configured to transmit and to receivewireless signals (e.g., RF, Bluetooth, UWB, and/or the like) accordingto the respective wireless protocols. According to various aspects, RFmay be utilized to efficiently transfer data with fewer errors. In someaspects, data transmission techniques including encryption/decryption,forward error correction, and/or the like may be instituted. Accordingto an alternative aspect, the wireless system 230 may be substitutedwith a second IR system and a multiplexer (not shown). The indicator 232may include a light emitting diode, indicator light, and/or the like.The location system 234 may include a Global Positioning System (GPS), aGlobal Navigation Satellite System (GLONASS), a Wi-Fi locating system,and/or the like. The user interface system may include a display 244and/or user interface controls 246 configured to receive control inputsfor transmission via the input/output hardware 208 and to displayoutputs received from the input/output hardware 208.

The network interface hardware 210 may generally provide the controldevice 200 with an ability to interface with one or more externaldevices, such as, for example, a medical facility server, a nursestation, and/or the like. Communication with external devices may occurusing various communication ports (not shown). An illustrativecommunication port may be attached to a communications network, such asthe Internet, an intranet, a local network, a direct connection, and/orthe like.

It should be understood that in some embodiments, the input/outputhardware 208 and the network interface hardware 210 may be combined intoa single device that allows for communications with other devices,regardless of whether such other devices are located within the controldevice 200.

It should be understood that the components illustrated in FIG. 2A aremerely illustrative and are not intended to limit the scope of thepresent disclosure. More specifically, while the components in FIG. 2Aare illustrated as residing within the control device, this is anon-limiting example. In some embodiments, one or more of the componentsmay reside external to the control device. Similarly, one or more of thecomponents may be embodied in other devices not specifically describedherein. Furthermore, various control devices are described herein (e.g.,FIG. 3) and are non-limiting examples. Other control devices may includea user's personal cell-phone, a nurse's call system device, and/or thelike with auxiliary line-of-sight communication channel capabilities(e.g., adapter).

FIG. 2B depicts illustrative internal components of a medical device 250that are communicatively coupled to one another to provide wireless linkpairing authentication with a control device, according to one or moreembodiments of the present disclosure. As shown in FIG. 2B, the medicaldevice 250 may include a local interface 252 (e.g., a bus) thatcommunicatively interconnects the various components, including, but notlimited to, a processing device 254, memory 256, input/output hardware258, network interface hardware 260, and/or a data storage device 262.

The processing device 254, such as a computer processing unit (CPU), maybe the central processing unit of the medical device 250, performingcalculations and logic operations required to execute a program. Theprocessing device 254, alone or in conjunction with one or more of theother elements disclosed in FIG. 2B, is an illustrative processingdevice, computing device, processor, or combination thereof, as suchterms are used in this disclosure.

The memory 256, such as read only memory (ROM) and random access memory(RAM), may constitute illustrative memory devices (i.e., non-transitory,processor-readable storage media). Such memory 256 may include one ormore programming instructions thereon that, when executed by theprocessing device 254, cause the processing device 254 to completevarious processes, such as the processes described herein. Optionally,the program instructions may be stored on a tangible computer-readablemedium such as a digital disk, flash memory, a memory card, a USB drive,an optical disc storage medium (e.g., Blu-ray™, CD, DVD), and/or othernon-transitory processor-readable storage media.

In some embodiments, the program instructions contained on the memory256 may be embodied as a plurality of software modules, where eachmodule provides programming instructions for completing one or moretasks. For example, as shown in FIG. 2B, the memory 256 may contain oneor more of operating logic 264, communications logic 266, and movementlogic 268. It should be understood that the various logic modulesdescribed herein with respect to FIG. 2B are merely illustrative, andthat other logic modules, including logic modules that combine thefunctionality of two or more of the modules described hereinabove, maybe used without departing from the scope of the present disclosure.

Still referring to FIG. 2B, the data storage device 262, which maygenerally be a storage medium that is separate from the memory 256, maycontain a data repository for storing electronic data and/or the likerelating to the location of the medical device 250, an identification ofthe medical device 250, configuration settings, and/or the like. Thedata storage device 262 may be any physical storage medium, including,but not limited to, a hard disk drive (HDD), memory, removable storage,and/or the like. While the data storage device 262 is depicted as alocal device, it should be understood that the data storage device 262may be a remote storage device that is remotely located from the medicaldevice 250, such as, for example, a server computing device or the like.

Illustrative data that may be contained within the data storage device262 may include, for example, location data 270, configuration data 272,pairing data 274, and/or the like. Pairing data 226 may include one ormore control device identifiers to which the medical device 250 is orhas been authentically paired via the methods as described herein.

The input/output hardware 258 may generally include an IR system 278, awireless system 280, an indicator 282, and a location system 284. The IRsystem 278 may include an IR diode 288 (e.g., infrared LED) configuredto emit/transmit infrared light and a photo transistor 290 configured toreceive infrared light and to convert the infrared light into anelectric current (e.g., according to IR protocols). The IR system 278may be unidirectional (e.g., IR diode 288 shown in phantom as optional)or bidirectional (e.g., including the IR diode 288). Furthermore, thephoto transistor 290 may be omni-directional to receive misaligned(e.g., within a defined tolerance) and/or reflected (e.g., off a wall,an object within the room, and/or the like) optical signals. Accordingto various aspects the IR system 278 may include a transceiver module.The wireless system 280 may include a transceiver 292 configured totransmit and to receive wireless signals (e.g., RF, Bluetooth, UWB,and/or the like) according to the respective wireless protocols.According to various aspects, RF may be utilized to efficiently transferdata with fewer errors. In some aspects, data transmission techniquesincluding encryption/decryption, forward error correction, and/or thelike may be instituted. According to an alternative aspect, the wirelesssystem 280 may be substituted with a second IR system and a multiplexer(not shown). The indicator 282 may include a light emitting diode,indicator light, and/or the like. The location system 284 may include aGlobal Positioning System (GPS), a Global Navigation Satellite System(GLONASS), a Wi-Fi locating system, and/or the like.

The network interface hardware 260 may generally provide the medicaldevice 250 with an ability to interface with one or more externalcomponents, such as, for example, a medical facility server, a nursestation, and/or the like. Communication with external devices may occurusing various communication ports (not shown). An illustrativecommunication port may be attached to a communications network, such asthe Internet, an intranet, a local network, a direct connection, and/orthe like.

It should be understood that in some embodiments, the input/outputhardware 258 and the network interface hardware 260 may be combined intoa single device that allows for communications with other devices,regardless of whether such other devices are located within the medicaldevice 250.

It should be understood that the components illustrated in FIG. 2B aremerely illustrative and are not intended to limit the scope of thisdisclosure. More specifically, while the components in FIG. 2B areillustrated as residing within the medical device 250, this is anon-limiting example. In some embodiments, one or more of the componentsmay reside external to the medical device 250. Similarly, one or more ofthe components may be embodied in other devices not specificallydescribed herein.

FIG. 3 depicts an illustrative wireless link pairing authenticationsystem 300 including a rail-mounted lift 302 as a medical device and aplurality of remote devices 304, 306, 308, as control devices, accordingto one or more embodiments of the present disclosure. Referring to FIG.3, the rail-mounted lift 302 is coupled to a rail 310. According tovarious aspects, the rail 310 may extend along a ceiling of a room(e.g., Room A of FIG. 1), along a ceiling of more than one room (e.g.,Room A and Room B of FIG. 1), and/or the like. More specifically, therail-mounted lift 302 includes a lift unit 312 that is slidably coupledto the rail 310 via a carriage 314. The lift unit 312 may be used tosupport and/or lift a subject with a lifting strap 316 which is coupledto a motor (not shown) contained within the lift unit 312. The motorfacilitates extending or retracting the lifting strap 316 from the liftunit 312, thereby raising and lowering a subject attached to the liftingstrap 316. According to various embodiments, a subject may be attachedto the lifting strap 316 with a sling bar 318 or a similar accessoryattached to the lifting strap 316 via a coupling 317. The sling bar 318or a similar accessory may be attached to a harness or a sling in whichthe subject is positioned, thereby facilitating the lifting operation.

Various components of the rail-mounted lift 302, such as the lift unit312 and/or components thereof, may be operated with a tethered handcontrol unit 304, a wireless hand control unit 306 and/or a wall-mountedcontrol unit 308 communicatively coupleable to the lift unit 312. Inview of FIG. 3, the tethered hand control unit 304 may be directly wiredto the lift unit 312 and/or wirelessly coupled or paired to the liftunit 312 (e.g., according to the methods described herein) to facilitateremote operation of the rail-mounted lift 302. According to variousaspects, the tethered hand control unit 304 may include a display 320and one or more user interface controls 322A (e.g., to extend liftingstrap 316), 322B (e.g., to retract lifting strap 316). Similarly, thewireless hand control unit 306 may be wirelessly coupled or paired tothe lift unit 312 (e.g., according to the methods described herein) andmay include a display 324 and one or more user interface controls 326A(e.g., to extend lifting strap 316), 326B (e.g., to retract liftingstrap), 326C (e.g., to translate lift unit 312 in a first lateraldirection L1 along rail 310), 326D (e.g., to translate lift unit 312 ina second lateral direction L2 along rail 310), and the wall-mountedcontrol unit 308 may be wirelessly coupled or paired to the lift unit312 (e.g., according to the methods described herein) and may include adisplay 328 and one or more user interface controls 330A (e.g., toextend lifting strap 316), 330B (e.g., to retract lifting strap 316),330C (e.g., to translate lift unit 312 in a first lateral direction L1along rail 310), 330D (e.g., to translate lift unit 312 in a secondlateral direction L2 along rail 310). Further user interface controls ofthe wall-mounted control unit 308 may activate the lift unit 312, pair asubject with the lift unit 312, return the lift unit 312 to a “home”position/location, receive information from the lift unit 312 (e.g.,battery status, magnitude of load supported by the lift unit, and/or thelike), actuate an emergency stop of the lift unit 312, reset the liftunit 312, and/or the like.

Referring to FIGS. 4A and 4B, according to further aspects of thepresent disclosure, the rail-mounted lift 302 (e.g., FIG. 3) may beoperated with a sling bar control unit 400 positioned on the sling bar318 and/or a coupling control unit 410 positioned on the coupling 317attached to a distal “D” end of the lifting strap 316. The sling barcontrol unit 400 may be wirelessly coupled or paired to the lift unit312 (e.g., according to the methods described herein) and may includeone or more user interface controls 402A (e.g., to extend lifting strap316), 402B (e.g., to retract lifting strap 316). Similarly, the couplingcontrol unit 410 may be wirelessly coupled or paired to the lift unit312 (e.g., according to the methods described herein) and may includeone or more user interface controls 412A (e.g., to extend lifting strap316), 412B (e.g., to retract lifting strap 316).

In light of FIGS. 3, 4A and 4B, a plurality of control devices (e.g., atethered hand control unit 304, a wireless hand control unit 306, awall-mounted control unit 308, a sling bar control unit 400, a couplingcontrol unit 410, and/or the like) may be either already physicallypresent in a room, physically brought into the room, and/or physicallytaken out of the room.

According to some aspects of the present disclosure, a medical device(e.g., the rail-mounted lift 302) may be fixedly positioned within aroom. In such aspects, referring to FIGS. 3 and 4B, control devices thatphysically remain in that room (e.g., wall-mounted control unit 308) andphysically remain coupled to the medical device itself in that room(e.g., tethered hand control unit 304, coupling control unit 410),remain in the line-of-sight of the medical device and the medical devicemay be configured to authenticate and remain paired with all suchcontrol devices. For example, the rail-mounted lift 302 may storepairing data (FIG. 2B, reference 274, e.g., associated CD IDs in a fixedpairings file), in its data storage device (FIG. 2B, reference 262) foreach control devices that physically remains in its room and/orphysically remains coupled to the rail-mounted lift 302. Further in suchaspects, referring to FIGS. 3 and 4A, one or more control devices maynot physically remain in that room (e.g., wireless hand control unit306, sling bar control unit 400). In such aspects, the medical devicemay be configured to not only authenticate and pair with such controldevices as they are brought into a room but also periodically orcontinually monitor authenticated pairings with such control devices.Periodically, as described herein, may refer to a regularly occurringinterval or time period (e.g., every “X” seconds, every “Y” minutes,and/or the like). Continuing the example, the rail-mounted lift 302 maystore pairing data (e.g., FIG. 2B, reference 274, e.g., associated CDIDs in a transient pairings file), in its data storage device (e.g.,FIG. 2B, reference 262) for each control device that may not physicallyremain in its room and the rail-mounted lift 302 may periodicallydetermine whether each authenticated control device identifier (e.g., CDID) is still being received over its optical communication channel.According to various aspects, if an authenticated control deviceidentifier (e.g., stored in the transient pairings file) is still beingoptically received, the medical device (e.g., rail-mounted lift) mayremain authentically paired with that control device and if theauthenticated control device identifier is not still being opticallyreceived, the medical device may automatically disassociate from thatcontrol device (e.g., control device considered as physically taken outof the room).

Further in light of FIGS. 3, 4A, and 4B, a medical device fixedlypositioned within a room may be configured to establish a hierarchy foraccepting control inputs (e.g., received at or near the same time) froma plurality of authentically paired control devices. For example, themedical device may be configured to give priority to a control inputreceived from a first grouping including control devices physicallyremaining in a room (e.g., a tethered hand control unit 304, awall-mounted control unit 308, and/or a coupling control unit 410) overa control input received from a second grouping including controldevices that may not physically remain in the room (e.g., a wirelesshand control unit 306 and/or a sling bar control unit 400). Further insuch an example, the medical device may be configured to give priorityto a control input received from control devices within the firstgrouping (e.g., tethered hand control unit 304 over coupling controlunit 410 over wall-mounted control unit 308, and/or the like) and/orcontrol devices within the second grouping (e.g., sling bar control unit400 over wireless hand control unit 306, and/or the like). Here, itshould be appreciated that such described hierarchies are non-limitingexamples and that other hierarchies may be established.

According to other aspects of the present disclosure, a medical device(e.g., a rail-mounted lift 302) may not be fixedly positioned within aroom. For example, a lift unit may be moved along a rail 310 (FIG. 3)from one room (e.g., FIG. 1, Room A) to another room (e.g., FIG. 1, RoomB). In such aspects, referring to FIGS. 3 and 4B, control devices thatphysically remain coupled to the medical device itself (e.g., tetheredhand control unit 304, coupling control unit 410), remain in theline-of-sight of the medical device and the medical device may beconfigured to authenticate and remain paired with all such controldevices. For example, the rail-mounted lift 302 may store pairing data(FIG. 2B, reference 274, e.g., associated CD IDs in a fixed pairingsfile), in its data storage device (FIG. 2B, reference 262) for eachcontrol devices that physically remains coupled to the rail-mounted lift302. Further in such aspects, referring to FIGS. 3 and 4A, one or morecontrol devices may not be physically coupled to the medical deviceitself. This may include control devices that physically remain in agiven room (e.g., wall-mounted control units 308) and/or control devicesthat may not physically remain in any given room (e.g., wireless handcontrol unit 306, sling bar control unit 400). In such aspects, themedical device may be configured to not only authenticate and pair withsuch control devices but also periodically or continually monitorauthenticated pairings with such control devices. Continuing theexample, the rail-mounted lift 302 may store pairing data (e.g., FIG.2B, reference 274, e.g., associated CD IDs in a transient pairingsfile), in its data storage device (e.g., FIG. 2B, reference 262) foreach control device that physically remains in a given room and that maynot physically remain in any given room and the rail-mounted lift 302may periodically determine whether each authenticated control deviceidentifier (e.g., CD ID) is still being received over its opticalcommunication channel. According to various aspects, upon detectingmovement (e.g., translation along rail 310) the medical device may beconfigured to continually monitor authenticated pairings with suchcontrol devices. Accordingly, if an authenticated control deviceidentifier (e.g., CD ID of a wireless hand control unit 306 being usedto translate or move the rail-mounted lift 302 between rooms, CD ID of asling bar control unit 400 being moved with the rail-mounted lift 302between rooms) is still being optically received, the medical device(e.g., rail-mounted lift) may remain authentically paired with thecontrol device(s) and if the authenticated control device identifier(e.g., CD ID of a wall-mounted control unit 308 in a former room, CD IDof a sling bar control unit 400 not moved to a new room) is not stillbeing optically received, the medical device may automaticallydisassociate from that control device(s). Further in such an aspect, themedical device may be configured to authenticate and pair with newcontrol devices (e.g., wall-mounted control unit 308 in new room) as themedical device transitions between rooms.

Further in light of FIGS. 3, 4A, and 4B, a medical device not fixedlypositioned within a room may be configured to establish a hierarchy foraccepting control inputs (e.g., received at or near the same time) froma plurality of authentically paired control devices. For example, themedical device may be configured to give priority to a control inputreceived from a first grouping including control devices that physicallyremain coupled to the medical device itself (e.g., a tethered handcontrol unit 304, a coupling control unit 410) over a control inputreceived from a second grouping including control devices thatphysically remain in a given room (e.g., wall-mounted control units 308)and/or control devices that may not physically remain in any given room(e.g., wireless hand control unit 306, sling bar control unit 400). Inanother example, the first grouping may include a control device beingused to move the medical device between rooms (e.g., wireless handcontrol unit 306). Here, with respect to a rail-mounted lift 302, it maybe desired to use a wireless hand control unit 306 over a tethered handcontrol unit 304 and/or a coupling control unit 410 to move therail-mounted lift 302 between rooms. Further in such an example, themedical device may be configured to give priority to a control inputreceived from control devices within the first grouping (e.g., tetheredhand control unit 304 or wireless hand control unit 306 over couplingcontrol unit 410, and/or the like) and/or control devices within thesecond grouping (e.g., wireless hand control unit 306 over sling barcontrol unit 400 over wall-mounted control unit 308, and/or the like).Here, it should be appreciated that such described hierarchies arenon-limiting examples and that other hierarchies may be established.

FIG. 5 depicts a flow diagram of an illustrative method 500 for pairinga medical device and a control device using an optical communicationchannel, according to one or more embodiments of the present disclosure.The pairing may include a one-way authentication of the medical devicewith a control device (e.g., left side of FIG. 5), a one-wayauthentication of the control device with a medical device (e.g., rightside of FIG. 5), or a two-way authentication of the medical device andthe control device (e.g., both sides of FIG. 5).

Referring to FIG. 5, a medical device MD_(X) may authenticate andautomatically pair with a control device. At block 502, a medical deviceMD_(X) may not be associated with and/or in the line-of-sight of anycontrol device. At block 504, the medical device MD_(X) may periodicallytransmit its identifier MD_(X) ID over its optical communication channel(e.g., IR channel) and wireless communication channel (e.g., RFchannel). Periodically as described herein, may refer to a regularlyoccurring interval or time period (e.g., every “X” seconds, every “Y”minutes, and/or the like). According to further aspects, the medicaldevice MD_(X) may be configured to manually transmit its identifierMD_(X) ID (e.g., upon a user actuating a transmit ID button on themedical device MD_(X)) over its optical communication channel (e.g., IRchannel) and wireless communication channel (e.g., RF channel). At block506, the medical device MD_(X) may periodically sniff for incomingcontrol device identifiers (e.g., CD IDs) over its optical communicationchannel. According to further aspects, the medical device MD_(X) may beconfigured to manually sniff for incoming control device identifiers(e.g., CD IDs) over its optical communication channel (e.g., upon a useractuating a receive ID button on the medical device MD_(X)). At block508, the medical device MD_(X) and a control device CD_(X) may bepositioned in a line-of-sight of one another. At block 510, the medicaldevice MD_(X) may receive a control device identifier CD_(X) ID over itsoptical communication channel. At block 512, the medical device MD_(X)may scan its wireless communication channel for the control deviceidentifier CD_(X) ID. At decision block 514, the medical device MD_(X)may determine whether it is receiving the same control device identifierCD_(X) ID over its optical communication channel and its wirelesscommunication channel. If it is determined, at decision block 514, thatthe received control device identifier CD_(X) ID does not match anycontrol device identifier being received over its wireless communicationchannel, the medical device MD_(X) may continue to periodically snifffor incoming control device identifiers (e.g., CD IDs) over its opticalcommunication channel at block 506. If it is determined, at decisionblock 514, that the optically received control device identifier CD_(X)ID does match a control device identifier being received over itswireless communication channel, the medical device MD_(X) mayautomatically associate with the control device CD_(X) over its wirelesscommunication channel at block 516. According to various aspects, themedical device MD_(X) may store the association as pairing data (FIG.2B, reference 276) in its data storage device (FIG. 2B, reference 262).At block 518 (e.g., shown in phantom as optional), the medical deviceMD_(X) may display a visual indicator of its association with a controldevice. According to some aspects, the visual indicator may be a lightemitting diode (LED) that illuminates when the medical device MD_(X) isassociated with a control device. According to another aspect, thevisual indicator may flash when the medical device MD_(X) is sniffingfor a control device over its optical channel and illuminate withoutflashes when the medical device MD_(X) is associated with a controldevice over its wireless channel. According to yet further aspects, thevisual indicator may include a display that indicates the controldevice(s) to which it is associated. At block 520, after beingauthentically paired with the control device CD_(X), the medical deviceMD_(X) may transmit status information to the control device CD_(X)and/or receive control inputs or commands from the control deviceCD_(X).

Referring still to FIG. 5, a control device CD_(X) may authenticate andautomatically pair with a medical device. At block 532, a control deviceCD_(X) may not be associated with and/or in the line-of-sight of anymedical device. At block 534, the control device CD_(X) may periodicallytransmit its identifier CD_(X) ID over its optical communication channel(e.g., IR channel) and wireless communication channel (e.g., RFchannel). Periodically as described herein, may refer to a regularlyoccurring interval or time period (e.g., every “X” seconds, every “Y”minutes, and/or the like). According to further aspects, the controldevice CD_(X) may be configured to manually transmit its identifierCD_(X) ID (e.g., upon a user actuating a transmit ID button on thecontrol device CD_(X)) over its optical communication channel (e.g., IRchannel) and wireless communication channel (e.g., RF channel). At block536, the control device CD_(X) may periodically sniff for incomingmedical device identifiers (e.g., MD IDs) over its optical communicationchannel. According to further aspects, the control device CD_(X) may beconfigured to manually sniff for incoming medical device identifiers(e.g., MD IDs) over its optical communication channel (e.g., upon a useractuating a receive ID button on the control device CD_(X)). At block508, the control device CD_(X) and a medical device MD_(X) may bepositioned in a line-of-sight of one another. At block 540, the controldevice CD_(X) may receive a medical device identifier MD_(X) ID over itsoptical communication channel. At block 542, the control device CD_(X)may scan its wireless communication channel for the medical deviceidentifier MD_(X) ID. At decision block 544, the control device CD_(X)may determine whether it is receiving the same medical device identifierMD_(X) ID over its optical communication channel and its wirelesscommunication channel. If it is determined, at decision block 544, thatthe optically received medical device identifier MD_(X) ID does notmatch any medical device identifier being received over its wirelesscommunication channel, the control device CD_(X) may continue toperiodically sniff for incoming medical device identifiers (e.g., MDIDs) over its optical communication channel at block 536. If it isdetermined, at decision block 544, that the received medical deviceidentifier MD_(X) ID does match a medical device identifier beingreceived over its wireless communication channel, the control deviceCD_(X) may automatically associate with the medical device MD_(X) overits wireless communication channel at block 546. According to variousaspects, the control device CD_(X) may store the association as pairingdata (FIG. 2A, reference 226) in its data storage device (FIG. 2A,reference 212). At block 548 (e.g., shown in phantom as optional), thecontrol device CD_(X) may display a visual indicator of its associationwith a medical device. According to some aspects, the visual indicatormay be a light emitting diode (LED) that illuminates when the controldevice CD_(X) is associated with a medical device. According to anotheraspect, the visual indicator may flash when the control device CD_(X) issniffing for a medical device over its optical channel and illuminatewithout flashes when the control device CD_(X) is associated with amedical device over its wireless channel. According to yet furtheraspects, the visual indicator may include a display that indicates themedical device(s) to which it is associated. At block 550, after beingauthentically paired with the medical device MD_(X), the control deviceCD_(X) may transmit or issue control inputs or commands to the medicaldevice MD_(X) and/or receive status information from the medical deviceMD_(X).

Still further, in view of FIG. 5, both the medical device MD_(X) mayauthenticate and automatically pair with the control device CD_(X) andthe control device CD_(X) may authenticate and automatically pair withthe medical device MD_(X), as described herein. According to variousaspects of the present disclosure, the medical device MD_(X) may nottransmit status information to the control device CD_(X) and/or receivecontrol inputs or commands from the control device CD_(X) and thecontrol device CDX may not transmit or issue control inputs or commandsto the medical device MDX and/or receive status information from themedical device MDX until such two-way authentication has occurred.

FIG. 6 depicts a flow diagram of an illustrative method 600 for pairinga medical device and a control device using an optical communicationchannel, according to one or more embodiments of the present disclosure.In particular, FIG. 6 utilizes a separate optical transmitter OT (e.g.,IR transmitter) to authentically pair the medical device and the controldevice. For example, an optical transmitter OT_(Y) associated with roomY may broadcast a room identifier R_(Y) ID as a beacon to the medicaldevice(s) and the control device(s) within room Y such that only devicesthat receive the same beacon will attempt to pair with one another.According to various aspects, the optical transmitter OT may include ahigh power IR transmitter to ensure that the medical device(s) and thecontrol device(s) receive the optical signal. According to furtheraspects, the optical transmitter OT may be physically located (e.g.,ceiling of room, wall of room, and/or the like) to ensure that themedical device(s) and the control device(s) receive the optical signal.According to some aspects, a separate device within the room (e.g., thewall-mounted control unit 308, of FIG. 3) may function in a mannersimilar to the optical transmitter OT as described herein. Similar toFIG. 5, the pairing may include a one-way authentication of the medicaldevice with a control device (e.g., left side of FIG. 6), a one-wayauthentication of the control device with a medical device (e.g., rightside of FIG. 6), or a two-way authentication of the medical device andthe control device (e.g., both sides of FIG. 6).

Referring to FIG. 6, a medical device MD_(X) may authenticate andautomatically pair with a control device using a separate opticaltransmitter. At block 602, a medical device MD_(X) may not be associatedwith and/or in the line-of-sight of any control device CD and/or anyoptical transmitter OT (e.g., an IR transmitter). At block 604, anoptical transmitter OT_(Y) may periodically transmit its room identifierR_(Y) ID over its optical communication channel (e.g., IR channel).Periodically as described herein, may refer to a regularly occurringinterval or time period (e.g., every “X” seconds, every “Y” minutes,and/or the like). According to further aspects, the optical transmitterOT_(Y) may be configured to manually transmit its room identifier R_(Y)ID (e.g., upon a user actuating a transmit ID button on the opticaltransmitter OT_(Y)) over its optical communication channel (e.g., IRchannel). At block 606, the medical device MD_(X) may periodically snifffor incoming room identifiers (e.g., R IDs) over its opticalcommunication channel (e.g. IR channel). According to further aspects,the medical device MD_(X) may be configured to manually sniff forincoming room identifiers (e.g., R IDs) over its optical communicationchannel (e.g., upon a user actuating a receive ID button on the medicaldevice MD_(X)). At block 608, the medical device MD_(X) and a controldevice CD_(X) may be positioned in the line-of-sight of the opticaltransmitter OT_(Y). At block 610, the medical device MD_(X) may receivethe room identifier R_(Y) ID over its optical communication channel. Atblock 612, the medical device MD_(X) may periodically transmit itsidentifier MD_(X) ID with the optically received room identifier R_(Y)ID over its wireless communication channel (e.g., RF channel). Accordingto further aspects, the medical device MD_(X) may be configured tomanually transmit its identifier MD_(X) ID with the optically receivedroom identifier R_(Y) ID (e.g., upon a user actuating a transmit IDbutton on the medical device MD_(X)) over its wireless communicationchannel (e.g., RF channel). At block 614, the medical device MD_(X) mayscan its wireless communication channel for the optically received roomidentifier R_(Y) ID. At decision block 616, the medical device MD_(X)may determine whether it is receiving a same room identifier R_(Y) IDover its optical communication channel and its wireless communicationchannel. If it is determined, at decision block 616, that the opticallyreceived room identifier R_(Y) ID does not match any room identifierbeing received over its wireless communication channel, the medicaldevice MD_(X) may continue to periodically sniff for incoming roomidentifiers (e.g., R IDs) over its optical communication channel atblock 606. If it is determined, at decision block 616, that theoptically received room identifier R_(Y) ID does match a room identifierbeing received over its wireless communication channel, the medicaldevice MD_(X) may determine a control device identifier CD_(X) IDreceived with the matching R_(Y) ID over its wireless communicationnetwork at block 618. At block 620, the medical device MD_(X) mayautomatically pair with the control device CD_(X) over its wirelesscommunication channel. According to various aspects, the medical deviceMD_(X) may store the association as pairing data (FIG. 2B, reference276) in its data storage device (FIG. 2B, reference 262). At block 622(e.g., shown in phantom as optional), the medical device MD_(X) maydisplay a visual indicator of its association with a control device.According to some aspects, the visual indicator may be a light emittingdiode (LED) that illuminates when the medical device MD_(X) isassociated with a control device. According to another aspect, thevisual indicator may flash when the medical device MD_(X) is sniffingfor a room identifier over its optical channel and illuminate withoutflashes when the medical device MD_(X) is associated with a controldevice over its wireless channel. According to yet further aspects, thevisual indicator may include a display that indicates the controldevice(s) to which it is associated. At block 624, after beingauthentically paired with the control device CD_(X), the medical deviceMD_(X) may transmit status information to the control device CD_(X)and/or receive control inputs or commands from the control deviceCD_(X).

Referring still to FIG. 6, a control device CD_(X) may authenticate andautomatically pair with a medical device using a separate opticaltransmitter. At block 632, a control device CD_(X) may not be associatedwith and/or in the line-of-sight of any medical device MD and/or anyoptical transmitter OT (e.g., an IR transmitter). At block 604, anoptical transmitter OT_(Y) may periodically transmit its room identifierR_(Y) ID over its optical communication channel (e.g., IR channel).Periodically as described herein, may refer to a regularly occurringinterval or time period (e.g., every “X” seconds, every “Y” minutes,and/or the like). According to further aspects, the optical transmitterOT_(Y) may be configured to manually transmit its room identifier R_(Y)ID (e.g., upon a user actuating a transmit ID button on the opticaltransmitter OT_(Y)) over its optical communication channel (e.g., IRchannel). At block 636, the control device CD_(X) may periodically snifffor incoming room identifiers (e.g., R IDs) over its opticalcommunication channel (e.g. IR channel). According to further aspects,the control device CD_(X) may be configured to manually sniff forincoming room identifiers (e.g., R IDs) over its optical communicationchannel (e.g., upon a user actuating a receive ID button on the controldevice CD_(X)). At block 608, the control device CD_(X) and a medicaldevice MD_(X) may be positioned in the line-of-sight of the opticaltransmitter OT_(Y). At block 640, the control device CD_(X) may receivethe room identifier R_(Y) ID over its optical communication channel. Atblock 642, the control device CD_(X) may periodically transmit itsidentifier CD_(X) ID with the optically received room identifier R_(Y)ID over its wireless communication channel (e.g., RF channel). Accordingto further aspects, the control device CD_(X) may be configured tomanually transmit its identifier CD_(X) ID with the optically receivedroom identifier R_(Y) ID (e.g., upon a user actuating a transmit IDbutton on the control device CD_(X)) over its wireless communicationchannel (e.g., RF channel). At block 644, the control device CD_(X) mayscan its wireless communication channel for the optically received roomidentifier R_(Y) ID. At decision block 646, the control device CD_(X)may determine whether it is receiving a same room identifier R_(Y) IDover its optical communication channel and its wireless communicationchannel. If it is determined, at decision block 646, that the opticallyreceived room identifier R_(Y) ID does not match any room identifierbeing received over its wireless communication channel, the controldevice CD_(X) may continue to periodically sniff for incoming roomidentifiers (e.g., R IDs) over its optical communication channel atblock 636. If it is determined, at decision block 646, that theoptically received room identifier R_(Y) ID does match a room identifierbeing received over its wireless communication channel, the controldevice CD_(X) may determine a medical device identifier MD_(X) IDreceived with the matching R_(Y) ID over its wireless communicationnetwork at block 648. At block 650, the control device CD_(X) mayautomatically pair with the medical device MD_(X) over its wirelesscommunication channel. According to various aspects, the control deviceCD_(X) may store the association as pairing data (FIG. 2A, reference226) in its data storage device (FIG. 2A, reference 212). At block 652(e.g., shown in phantom as optional), the control device CD_(X) maydisplay a visual indicator of its association with a medical device.According to some aspects, the visual indicator may be a light emittingdiode (LED) that illuminates when the control device CD_(X) isassociated with a medical device. According to another aspect, thevisual indicator may flash when the control device CD_(X) is sniffingfor a room identifier over its optical channel and illuminate withoutflashes when the control device CD_(X) is associated with a medicaldevice over its wireless channel. According to yet further aspects, thevisual indicator may include a display that indicates the medicaldevice(s) to which it is associated. At block 654, after beingauthentically paired with the medical device MD_(X), the control deviceCD_(X) may transmit or issue control inputs or commands to the medicaldevice MD_(X) and/or receive status information from the medical deviceMD_(X).

Still further, in view of FIG. 6, both the medical device MD_(X) mayauthenticate and automatically pair with the control device CD_(X) andthe control device CD_(X) may authenticate and automatically pair withthe medical device MD_(X), as described herein. According to variousaspects of the present disclosure, the medical device MD_(X) may nottransmit status information to the control device CD_(X) and/or receivecontrol inputs or commands from the control device CD_(X) and thecontrol device CD_(X) may not transmit or issue control inputs orcommands to the medical device MD_(X) and/or receive status informationfrom the medical device MD_(X) until such two-way authentication hasoccurred.

Yet further in view of FIG. 6, according to an alternative aspect, theoptical transmitter OT may be substituted with an Ultra-Wide Band (UWB)transmitter. Similar to above, the UWB transmitter may broadcast a roomidentifier RX ID as a location beacon to the devices (e.g., medicaldevice(s) and the control device(s)) within room X and the devices mayuse an UWB communication channel to receive the location beacon, suchthat only devices that receive the same beacon will attempt to pair withone another.

FIG. 7 depicts a flow diagram of an illustrative method 700 forassociating and disassociating medical devices and control devices,according to one or more embodiments of the present disclosure.Referring to FIG. 7, at block 702, a medical device MD_(X) may beauthentically paired with a control device CD_(X) over a wirelesscommunication channel (e.g., RF channel) and/or the control deviceCD_(X) may be authentically paired with the medical device MD_(X) overthe wireless communication channel, as described herein. At decisionblock 704, the medical device MD_(X) may determine whether an opticalcommunication channel (e.g., IR channel) with the authentically pairedcontrol device CD_(X) is weak (e.g., below a predetermined thresholdoptical signal strength) or the control device CD_(X) may determinewhether the optical communication channel with the authentically pairedmedical device MD_(X) is weak (e.g., below a predetermined thresholdoptical signal strength). In such aspects, the medical device MD_(X)and/or the CD_(X) may be configured to use the optical communicationchannel as a cue that the medical device MD_(X) and/or the CD_(X) isbeing repositioned within the medical facility (e.g., rail-mounted lift302 of FIG. 3 translated into adjoining room, wireless hand control unit306 of FIG. 3 carried outside of room by a caregiver, and/or the like).If it is determined at decision block 704 that the optical communicationchannel is weak, the medical device MD_(X) may be configured toautomatically disassociate from the control device CD_(X) over thewireless communication channel and/or the control device CD_(X) may beconfigured to automatically disassociate from the medical device MD_(X)over the wireless communication channel at block 706. According tofurther aspects, the medical device MD_(X) may be configured to manuallydisassociate (e.g., upon a user actuating a disassociate button on themedical device MD_(X)) from a control device CD_(X) and/or the controldevice CD_(X) may be configured to manually disassociate (e.g., upon auser actuating a disassociate button on the control device CD_(X)) froma medical device MD_(X). Upon disassociation, at block 708, the medicaldevice MD_(X) may scan its optical communication channel for controldevice identifiers (e.g., CD IDs) and, at block 710, the medical deviceMDX may initiate an authenticated pairing with a new control device(e.g., CD_(Y)), as described herein. Similarly upon disassociation, atblock 708, the control device CD_(X) may scan its optical communicationchannel for medical device identifiers (e.g., MD IDs) and, at block 712,the control device CD_(X) may initiate an authenticated pairing with anew medical device (e.g., MD_(Y)), as described herein. If it isdetermined at decision block 704 that the optical communication channelis not weak, the medical device MD_(X) may determine whether a wirelesscommunication channel (e.g., RF channel) with the authentically pairedcontrol device CD_(X) is weak (e.g., below a predetermined thresholdwireless signal strength) and/or the control device CD_(X) may determinewhether the wireless communication channel with the authentically pairedmedical device MDX is weak (e.g., below a predetermined thresholdwireless signal strength) at decision block 714. If it is determined atdecision block 714 that the wireless communication channel is weak, themedical device MD_(X) may be similarly configured to automaticallydisassociate from the control device CD_(X) over the wirelesscommunication channel and/or the control device CD_(X) may be similarlyconfigured to automatically disassociate from the medical device MD_(X)over the wireless communication channel at block 706. At block 708, themedical device MD_(X) may scan its optical communication channel forcontrol device identifiers (e.g., CD IDs) and, at block 710, the medicaldevice MD_(X) may initiate an authenticated pairing with a new ordifferent control device (e.g., CD_(Y)) as described. Likewise, at block708, the control device CD_(X) may scan its optical communicationchannel for medical device identifiers (e.g., MD IDs) and, at block 712,the control device CD_(X) may initiate an authenticated pairing with anew or different medical device (e.g., MD_(Y)) as described. Accordingto an alternative aspect (e.g., shown in phantom) the method may proceedfrom block 702 directly to decision block 714 and proceed as describedherein. In such an aspect, the medical device MD_(X) may remainauthentically paired with the control device CD_(X) over the wirelesscommunication channel irrespective of whether the optical communicationchannel with the authentically paired control device CD_(X) is weak orbroken and/or the control device CD_(X) may remain authentically pairedwith the medical device MD_(X) over the wireless communication channelirrespective of whether the optical communication channel with theauthentically paired medical device MD_(X) is weak or broken. Forexample, the medical device MD_(X) or the control device CD_(X) maymaintain communications (e.g., non-control based communications such asbattery status or the like) over the wireless communication channel withthe control device CD_(X) or the medical device MD_(X), respectively,despite the optical communication channel being weak or broken (e.g.,due to the control device CD_(X) or the medical device MD_(X),respectively, being in a cabinet or the optical communication path beingblocked or interfered with in some way). At decision block 714, if it isdetermined that the wireless communication channel is not weak themedical device MD_(X) may determine whether a new or different CD_(Y) IDis being received over its optical communication channel at decisionblock 716. According to an alternative aspect (e.g. shown in phantom)the method may proceed from block 702 directly to decision block 716. Ifit is determined at decision block 716 that no new or different CD_(Y)ID is being received over its optical communication channel, the medicaldevice MD_(X) may remain authentically paired with the control deviceCD_(X) over its wireless communication channel at block 702. If it isdetermined at decision block 716 that a new or different CD_(Y) ID isbeing received over its optical communication channel, the medicaldevice MD_(X) may be configured to scan its optical channel for theCD_(X) ID associated with its authentically paired control device CD_(X)at block 718. At decision block 720, if it is determined that the CD_(X)ID has been detected, the medical device MD_(X) may remain authenticallypaired with the control device CD_(X) over its wireless communicationchannel at block 702. According to the aspects described in FIG. 7, themedical device MD_(X) may only be authentically paired with one controldevice. Such an embodiment may prevent the medical device MDX fromreceiving control inputs (e.g., simultaneous control inputs, conflictingcontrol inputs, and/or the like) from more than one control device.Here, it should be appreciated that other embodiments may include themedical device MD_(X) as authentically paired with multiple controldevices (e.g., dual lift capability, two control devices operating intandem). At decision block 720, if it is determined that the CD_(X) IDhas not been detected, the medical device MD_(X) may automaticallydisassociate from the control device CD_(X) over its wirelesscommunication channel at block 722, and at block 710, the medical deviceMD_(X) may initiate an authenticated pairing with the new or differentcontrol device CD_(Y), as described. Similarly, at decision block 724,the control device CD_(X) may determine whether a new or differentMD_(Y) ID is being received over its optical communication channel. Insuch aspects, as depicted in FIG. 7, decision block 716 may be apass-through to decision block 724 (e.g., the control device CD_(X) maynot monitor its optical communication channel for any new or differentcontrol device CD_(Y)). As such, similar to as described herein, thecontrol device CD_(X), may determine whether a new or different MD_(Y)ID is being received over its optical communication channel directlyfrom block 702 and/or if it is determined at decision block 714 that thewireless communication channel is not weak. If it is determined atdecision block 724 that no new or different MD_(Y) ID is being receivedover its optical communication channel, the control device CD_(X) mayremain authentically paired with the medical device MD_(X) over itswireless communication channel at block 702. If it is determined atdecision block 724 that a new or different MD_(Y) ID is being receivedover its optical communication channel, the control device CD_(X) may beconfigured to scan its optical channel for the MD_(X) ID associated withits authentically paired medical device MD_(X) at block 726. At decisionblock 728, if it is determined that the MD_(X) ID has been detected, thecontrol device CD_(X) may remain authentically paired with the medicaldevice MD_(X) over its wireless communication channel at block 702.According to the aspects described in FIG. 7, the control device CD_(X)may only be authentically paired with one medical device. Such anembodiment may prevent the control device CD_(X) from transmittingcontrol inputs to more than one medical device. Here, it should beappreciated that other embodiments may include the control device CD_(X)as authentically paired with multiple medical devices (e.g. in the sameroom). At decision block 728, if it is determined that the MD_(X) ID hasnot been detected, the control device CD_(X) may automaticallydisassociate from the medical device MD_(X) over its wirelesscommunication channel at block 730, and at block 712, the control deviceCD_(X) may initiate an authenticated pairing with the new or differentmedical device MD_(Y), as described.

FIG. 8 depicts a flow diagram of an illustrative method 800 for acontrol device to issue commands or control inputs to an authenticallypaired medical device, according to one or more embodiments of thepresent disclosure. According to various aspects, method 800 may beutilized for all control functions or only subject critical functions(e.g., actuating a motor, turning on a pump, and/or the like). Referringto FIG. 8, at block 802, a control device CD_(X) may be authenticallypaired with a medical device MD_(X) over its wireless communicationchannel, as described herein. At decision block 804, the control deviceCD_(X) may be configured to determine (e.g., based on inputs receivedvia user interface controls 246 of FIG. 2A) whether a command or controlinput is to be issued or transmitted to the medical device MD_(X). If itis determined that a command or control input is not to be issued ortransmitted to the medical device MD_(X), the control device CD_(X) mayremain paired with the MD_(X) over its wireless communication channel atblock 802. If it is determined that a command or control input is to beissued or transmitted to the medical device MD_(X), the control deviceCD_(X) may be configured to determine whether the wireless communicationchannel is weak (e.g., below a predetermined threshold wireless signalstrength) at decision block 806. If it is determined that the wirelesscommunication channel is weak, the control device CD_(X) may beconfigured to automatically disassociate from the medical device MDXover the wireless communication channel at block 808. At block 810(shown in phantom as an optional step), the control device CD_(X) may beconfigured to update its visual indicator to reflect the disassociation(e.g., LED off). If it is determined that the wireless communicationchannel is not weak, the control device CD_(X) may be configured, atblock 812, to ping the medical device MD_(X) over its opticalcommunication channel (e.g., transmit an inquiry token). According to analternative aspect (e.g., shown in phantom) the method may proceed fromdecision block 804 directly to block 812 and proceed as describedherein. At decision block 814, the control device CD_(X) may beconfigured to determine whether it has received a response (e.g.,response token, MD ID, and/or the like) from the medical device MD_(X)over its optical communication channel. If it is determined that thecontrol device CD_(X) has not received a response from the medicaldevice MD_(X), the control device CD_(X) may be configured, at block816, to not issue or transmit the command or control input to themedical device MD_(X). At block 818 (shown in phantom as an optionalstep), the control device CD_(X) may be configured to update its visualindicator to reflect a pairing issue with the medical device MD_(X)(e.g., medical device MD_(X) not within line-of-sight of control deviceCD_(X), indicator that the medical device MD_(X) must be re-located towithin the line-of-sight of the control device CD_(X) to execute acontrol function). If it is determined that the control device CD_(X)has received a response from the medical device MD_(X), the controldevice CD_(X) may be configured to, at block 820, issue the command orcontrol input to the medical device MD_(X) over its wirelesscommunication channel. According to such aspects, if a medical deviceMD_(X) is moved into an adjacent room (e.g., no longer withinline-of-sight of the control device CD_(X)) the control device CD_(X) isrendered unable to issue a command or control input to the medicaldevice (MDX) despite being otherwise able to over a strong wirelesscommunication channel.

According to another embodiment, referring back to FIGS. 2A and 2B, thecontrol device 200 may include a location system 234 and the medicaldevice 250 may include a location system 284. In such aspects, themedical device 250 and/or the control device 200 may be configured tofurther transmit their respective location information (e.g., MD LOC, CDLOC) with their respective identifiers (e.g., MD ID, CD ID) as describedherein. In such aspects, the medical device 250 may be configured tocompare a received CD LOC with its MD LOC as part of its determinationas to whether to authentically pair with a control device. In someaspects, an initial range (e.g., about 2 m to about 5 m radius) may beused for initial authentication and a control range (e.g., average sizeof room) may be used for disassociation. In further aspects, the medicaldevice 250 may be configured to adjust/correct its MD LOC as well as thereceived CD LOC using a medical facility location MF LOC location beaconwith known coordinates. Similarly, the control device 200 may beconfigured to compare a received MD LOC with its CD LOC as part of itsdetermination as to whether to authentically pair with a medical device.Again, an initial range (e.g., about 2 m to about 5 m radius) may beused for initial authentication and a control range (e.g., average sizeof room) may be used for disassociation. Likewise, the control device200 may be configured to adjust/correct its CD LOC as well as thereceived MD LOC using a medical facility location MF LOC location beaconwith known coordinates. According to various embodiments, such aspectsmay be used to further confirm the other authentication methods asdescribed herein.

According to the various embodiments described herein, each of theoptical communication channel (e.g., IR channel) and the wirelesscommunication channel (e.g., RF channel) may be configured as asingle-path communication channel or a dual-path communication channel.Furthermore, although the line-of-sight communication channel isdescribed herein as an optical communication channel, the line-of sightcommunication channel may be any auxiliary line-of-sight communicationchannel that is guaranteed to be line-of-sight only. Namely, theline-of-sight communication channel is only accessible to the device tobe controlled (e.g., medical device) when visible from a control point(e.g., control device).

It should now be understood that the systems and methods describedherein are suitable for pairing a medical device and a control deviceusing a line-of-sight optical link (e.g., IR channel). In particular,the systems and methods described herein automatically authenticate aconfigurable, pairable wireless connection (e.g. RF channel) to be usedto execute control actions for a medical device (e.g., rail-mountedlift) to ensure that the control inputs are coming from a control device(e.g., a tethered hand control unit, a wireless hand control unit, awall-mounted control unit, a sling bar control unit, a coupling controlunit, and/or the like) located in the same room as the medical device.Such systems and methods ensure that the control inputs coming from thecontrol device are only directed to a medical device that is directlyobservable or visible to the control device user.

While particular embodiments have been illustrated and described herein,it should be understood that various other changes and modifications maybe made without departing from the spirit and scope of the claimedsubject matter. Moreover, although various aspects of the claimedsubject matter have been described herein, such aspects need not beutilized in combination. It is therefore intended that the appendedclaims cover all such changes and modifications that are within thescope of the claimed subject matter.

What is claimed is:
 1. A method for automatically pairing a medicaldevice with a control device, the method comprising: receiving, via afirst communication channel, an identifier associated with a controldevice within a line-of-sight of the medical device; receiving, via asecond communication channel different from the first communicationchannel, at least one identifier associated with at least one controldevice; determining that the identifier received over the firstcommunication channel matches an identifier of the at least oneidentifier received over the second communication channel; andautomatically pairing with the control device associated with thematching identifier over the second communication channel.
 2. The methodof claim 1, wherein the first communication channel is an opticalcommunication channel and the second communication channel is a wirelesscommunication channel.
 3. The method of claim 2, wherein the opticalcommunication channel is an infrared (IR) communication channel and thewireless communication channel is a radio frequency (RF) communicationchannel.
 4. The method of claim 1, further comprising: receiving controlinputs from the control device associated with the matching identifier,the control inputs for controlling a function of the medical device. 5.The method of claim 1, further comprising: determining that at least oneof the first communication channel or the second communication channelis associated with a signal below a predetermined threshold strength;and disassociating from the control device associated with the matchingidentifier.
 6. The method of claim 1, wherein the control deviceassociated with the matching identifier is a first control deviceassociated with a first identifier, and wherein the method furthercomprises: receiving, via the first communication channel, a secondidentifier associated with a second control device within theline-of-sight of the medical device; determining whether the firstidentifier is detectable over the first communication channel; andremaining paired with the first control device if the first identifieris detected over the first communication channel; or automaticallydisassociating from the first control device if the first identifier isnot detected over the first communication channel.
 7. The method ofclaim 6, further comprising: determining that the second identifierreceived over the first communication channel matches an identifier ofthe at least one identifier received over the second communicationchannel; and automatically pairing with the second control deviceassociated with the matching second identifier over the secondcommunication channel.
 8. A method for automatically pairing a controldevice with a medical device, the method comprising: receiving, via afirst communication channel, an identifier associated with a medicaldevice within a line-of-sight of the control device; receiving, via asecond communication channel different from the first communicationchannel, at least one identifier associated with at least one medicaldevice; determining that the identifier received over the firstcommunication channel matches an identifier of the at least oneidentifier received over the second communication channel; andautomatically pairing with the medical device associated with thematching identifier over the second communication channel.
 9. The methodof claim 8, wherein the first communication channel is an opticalcommunication channel and the second communication channel is a wirelesscommunication channel.
 10. The method of claim 9, wherein the opticalcommunication channel is an infrared (IR) communication channel and thewireless communication channel is a radio frequency (RF) communicationchannel.
 11. The method of claim 8, further comprising: transmittingcontrol inputs to the medical device associated with the matchingidentifier, the control inputs for controlling a function of the medicaldevice.
 12. The method of claim 8, further comprising: determining thatat least one of the first communication channel or the secondcommunication channel is associated with a signal below a predeterminedthreshold strength; and disassociating from the medical deviceassociated with the matching identifier.
 13. The method of claim 8,wherein the medical device associated with the matching identifier is afirst medical device associated with a first identifier, and wherein themethod further comprises: receiving, via the first communicationchannel, a second identifier associated with a second medical devicewithin the line-of-sight of the control device; determining whether thefirst identifier is detectable over the first communication channel; andremaining paired with the first medical device if the first identifieris detected over the first communication channel; or automaticallydisassociating from the first medical device if the first identifier isnot detected over the first communication channel.
 14. The method ofclaim 13, further comprising: determining that the second identifierreceived over the first communication channel matches an identifier ofthe at least one identifier received over the second communicationchannel; and automatically pairing with the second medical deviceassociated with the matching second identifier over the secondcommunication channel.
 15. The method of claim 8, further comprising:receiving, via at least one user interface control, a control input;sending, via the first communication channel, an inquiry token to themedical device associated with the matching identifier; determining, viathe first communication channel, whether a response token has beenreceived from the first medical device associated with the matchingidentifier; and transmitting the control input to the medical deviceassociated with the matching identifier if the response token has beenreceived over the first communication channel; or abstaining fromtransmitting the control input to the medical device associated with thematching identifier if the response token has not been received over thefirst communication channel.
 16. The method of claim 8, furthercomprising: updating a visual indicator to reflect that the medicaldevice is not within a line-of-sight of the control device.
 17. A methodfor automatically pairing devices, the method comprising: transmitting,via a transmitter positioned within a location, a location identifierover a first communication channel to devices with a line-of-sight ofthe transmitter; receiving, by a first device and a second device, thelocation identifier over the first communication channel; transmitting,by the first device, the location identifier and an identifierassociated with the first device over a second communication channel;transmitting, by the second device, the location identifier and anidentifier associated with the second device over the secondcommunication channel; scanning, by the first device and the seconddevice, the second communication channel for the location identifierreceived over the first communication channel; determining, by the firstdevice and the second device, that the location identifier received overthe first communication channel matches a location identifier on thesecond communication channel; determining, by the first device, thesecond device identifier associated with the matching locationidentifier and automatically pairing with the second device associatedwith the second device identifier over the second communication channel;and determining, by the second device, the first device identifierassociated with the matching location identifier, and automaticallypairing with the first device associated with the first deviceidentifier over the second communication channel.
 18. The method ofclaim 17, wherein the first communication channel is an opticalcommunication channel and the second communication channel is a wirelesscommunication channel.
 19. The method of claim 18, wherein the opticalcommunication channel is an infrared (IR) communication channel and thewireless communication channel is a radio frequency (RF) communicationchannel.
 20. The method of claim 17, wherein the first communicationchannel is an ultra-wide band communication channel.